Skip to content

Conversation

@pedrovgs
Copy link
Member

This PR is the first step to be able to make the project compatible with WASM. We here provide some fallback implementations and disable some complex functions and features but make build usabe on WASM.

My next iteration will focus on the features I had to disable to be able to use this project with Swift WASM.

@pedrovgs
Copy link
Member Author

pedrovgs commented Jan 19, 2026

@kateinoigakukun do you happen to know why the CI build is failing in this PR? I can see it passing locally 🤔

Screenshot 2026-01-19 at 15 05 44 Screenshot 2026-01-19 at 15 06 28

I guess it's a memory issue, but don't know if this is on the toolchain side or our side.

Copy link

@pacowong pacowong left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks. I mainly trust the test results and check some functions as it is impossible to review all functions in a short time.

@pedrovgs
Copy link
Member Author

Thanks for the review @pacowong I've just added one last commit fixing CI for WASM that was broken only on CI because of the usage of an unstable version. Yuta confirmed the version we have to use and CI should be passing now 😃

@pedrovgs pedrovgs merged commit bab1f10 into master Jan 20, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants